The path will change based on the platform that you install puppeteer on. install.js has methods for finding that path. Something like this should work:

const Downloader = require('puppeteer/utils/ChromiumDownloader');
const {chromium_revision} = require('puppeteer/package.json').puppeteer;
const info = Downloader.revisionInfo(Downloader.currentPlatform(), chromium_revision);
console.log(info);

info.executablePath will give you the binary's path. Useful when launching chrome: puppeter.launch({executablePath: info.executablePath}).

Hello, how can I do the same thing today ? The utils directory no longer exists. Thanks

@KaKi87 https://github.com/puppeteer/puppeteer/blob/master/src/BrowserFetcher.ts

@KaKi87 Puppeteer has an API for getting the path to the executable: https://github.com/GoogleChrome/puppeteer/blob/v1.1.1/docs/api.md#puppeteerexecutablepath

run in the directory where node_modules is located

node -e "console.log(require('puppeteer').executablePath())"

Example output on Linux:

/app/node_modules/puppeteer/.local-chromium/linux-686378/chrome-linux/chrome

downloaded location in debian linux for chrome is /home/user/.cache/puppeteer/chrome/linux-117.0.5938.92/chrome-linux64/ and it is not detected at all. I will recommend puppeeteer to tell the EXPECTED full dir in order to be able to rename it for that.